Hi Craig,

By default, it will no longer attempt to download a snapshot and the chain will sync from scratch. However, users can still set any JSON URL (if available) and this update shouldn't break existing configurations.

with xtz shots and marigold down, there is no longer any snapshot service compatible with this metadata. It would be nice if tznit could generate such a json to restore the previous functionality. Otherwise, I guess the json parsing logic in utils/config_generator.py can also be deleted.

This also allows them to use their closest region.

If metadata schema was updated to contain a region field, this could be automated as an extension of the existing python metadata handling code. This would be cool, but of course there has to be a need.

corrected spelling mistakes in charts/snapshotEngine/README.md

actually, we might want to delete the whole snapshotEngine chart. Unless you are planning to migrate tzinit snapshots to k8s, this is dead code.

Paris update to mkchain/tqchain/mkchain.py

Thanks. This could be its own PR? There are a few more things to do:

See examples:

Nairobi update:
39ef10c

Oxford update (actually blended in with a lot of unrelated changes):
d34dee0

Most notably, the parameters.yaml file needs to be updated with a set of parameters that works with paris. You can test by running mkchain with no parameters, and the resulting chart values should start a private chain running Paris protocol.

Thanks @nicolasochem - appreciate the feedback.

Marigold appears to be running for the moment, so we probably shouldn't remove the JSON functionality just yet. I've been considering possibilities and will (probably) add a new metadata option to select a tzinit.org region when a specific URL or JSON source is not provided. It'll therefore attempt to get a snapshot like it does now.

Good point about mkchain - I'll separate into a new PR.